-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update dependency next-transpile-modules to v10 - autoclosed #908
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
fccb8b2
to
84bebc9
Compare
84bebc9
to
ddcc204
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #908 +/- ##
=======================================
Coverage 65.40% 65.40%
=======================================
Files 15 15
Lines 318 318
Branches 130 130
=======================================
Hits 208 208
Misses 89 89
Partials 21 21 ☔ View full report in Codecov by Sentry. |
ddcc204
to
114328d
Compare
114328d
to
3f3abe6
Compare
3f3abe6
to
0dbf4fa
Compare
0dbf4fa
to
149c4ca
Compare
149c4ca
to
859dc75
Compare
34ae400
to
c060726
Compare
32827ed
to
999eec1
Compare
c060726
to
a1778dd
Compare
This PR contains the following updates:
9.1.0
->10.0.1
Release Notes
martpie/next-transpile-modules (next-transpile-modules)
v10.0.1
Compare Source
v10.0.0
Compare Source
Hello everyone! No breaking changes in this version, I just bumped it to make sure people are careful when upgrading to Next.js 13. Please make sure to read the additional notes below regarding the future of
next-transpile-modules
and Turbopack.If you appreciate my work, and if you can afford it, you (or better, your company) can show support by sponsoring me (or just buying me a beer 🙌).
Support for Next.js 13
Enjoy!
Experimental support for the
app/
directoryNext.js 13 comes with beta support for the new
app/
directory, and next-transpile-modules supports it.Please think twice before using this feature as it's still experimental and
next-transpile-modules
could break at any of Next.js commit.Note on Turbopack
Turbopack being in alpha,
next-transpile-modules
will not be supporting it. It may work out of the box, it may not, I will not work on it before it's more stable.Note on the future of
next-transpile-modules
andtranspilePackages
Next.js 13 comes with a new option called
transpilePackages
. This new experimental feature currently allows to transpile local and npm ES modules, so you might not neednext-transpile-modules
anymore, ifyou're ready to enable experimental features on Next.js.That said, and this is great news, the Next.js team is working on feature parity with
next-transpile-modules
, sonext-transpile-modules
will disappear some day in the future.There is no clear timeline yet, so in the meantime, I'll keep maintaining this plugin until:
transpilePackages
is not experimental anymoretranspilePackages
has feature parity withnext-transpile-modules
That's it!
Take care of yourselves and happy coding!
Configuration
📅 Schedule: Branch creation - "every weekday after 2:00 am before 6:00 am,every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.